Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

PR Description

Issue:
Creating an aaa_radius_attribute template fails if called_station_id is not provided in the playbook, even though the Catalyst Center API treats it as an optional field.

RCA:
The called_station_id field was marked as required: true in the module documentation, and the validation logic unconditionally checked its value against the allowed list — causing a failure when the value was None. Additionally, update and create payloads always included calledStationId regardless of whether it was provided, sending None to the API.

Fix:

• Changed called_station_id from required: true to required: false in the module documentation.
• Made the allowed-values validation conditional — only runs when called_station_id is explicitly provided.
• Payloads now preserve the existing calledStationId from Catalyst Center when no new value is provided.

Testing Done:

• Manual testing
• Unit tests
• [] Integration tests

Test cases covered: [Mention test case IDs or brief points]

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• All the sanity checks have been completed and the sanity test cases have been executed

Ansible Best Practices

• Tasks are idempotent (can be run multiple times without changing state)
• Variables and secrets are handled securely (e.g., using ansible-vault or environment variables)
• Playbooks are modular and reusable
• Handlers are used for actions that need to run on change

Documentation

• All options and parameters are documented clearly.
• Examples are provided and tested.
• Notes and limitations are clearly stated.

Screenshots (if applicable)

Notes to Reviewers